test(profiling): unflake test_copy_memory_stats - #19706
Open
KowalskiThomas wants to merge 2 commits into
Open
Conversation
🎉 All green!🧪 All tests passed 🔗 Commit SHA: 41b6359 | Docs | Datadog PR Page | Give us feedback! |
Codeowners resolved asResolved from the full PR diff against |
Dependency direction analysis
|
Circular import analysis
|
taegyunkim
approved these changes
Aug 14, 2026
taegyunkim
left a comment
Contributor
There was a problem hiding this comment.
Yeah I remember that we had to properly sort the pprof files as well.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR attempts to unflake
test_copy_memory_statswhich has been rarely (but still) failing lately. I suspect this is because there is a race between the sampling thread upgrading to fast copy memory and the uploader thread dumping stats to the file (which would explain why it's so rare).Something LLMs also suggested is to make sure we sort file names by their actual order and not just with
sorted, sincesortedwould sort lexicographically in which caseprofile.10would appear beforeprofile.2, so I also fixed that.